home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The 640 MEG Shareware Studio 2
/
The 640 Meg Shareware Studio CD-ROM Volume II (Data Express)(1993).ISO
/
bbs
/
mezz308a.zip
/
MEZANINE.DOC
< prev
next >
Wrap
Text File
|
1992-10-18
|
69KB
|
1,428 lines
METRO-MEZZANINE, Type III
Version 3.08
By Steven H. Lin
Copyright 1992 by Steven H. Lin
All rights reserved
GENERAL OPERATIONS MANUAL
-----------------------------------------------------------------------------
CONTENTS
1.0 Introduction
2.0 Registration
3.0 The Purpose of Metro-Mezzanine
4.0 Requirements
5.0 Installation
6.0 Setup
7.0 Operations
8.0 Variations
9.0 Product Support
10.0 Acknowledgements
11.0 Final Words
12.0 Registration Form
-----------------------------------------------------------------------------
1.0 INTRODUCTION
If you are a BBS aficionado type of system operator (sysop), then
Metro-Mezzanine may be for you. Testing more than one BBS program at a time,
or just running your usual one while testing another for whatever reason,
can be time- and space-consuming as you struggle with rearranging your hard
disk and other facets of your system to accomodate each BBS program as much
as you can without adversely affecting the others.
Metro-Mezzanine can help, by making access to the different BBS programs (or
even to just ONE, if you need a special customizable front-end program
between your mailer and your BBS) as painless as possible. In this age of
sophistication, making things more palatable is a definite plus.
1.1 Warning -
If you have never used a program from [The Deviant's Palace], then
you may be in for a massive shock. Please, if you suffer from an
angina pectoris condition, keep your supply of amyl nitrate or
nitroglycerin within easy reach. If you are using stronger
medications, like calcium channel blocking agents (most notably
verapamil) or ß-adrenoceptor blocking agents (AKA "beta blockers"),
you may want to have some experienced medical personnel nearby to
monitor your health condition as you set up Metro-Mezzanine. Use
Metro-Mezzanine at your own risk.
If you suffer from psychological problems or disabilities,
Metro-Mezzanine is not guaranteed to not injury your psyche. Use
Metro-Mezzanine at your own risk.
1.2 License Agreement -
The author of Metro-Mezzanine has taken every precaution to insure
that no harm or damage will occur on computer systems operating the
Metro-Mezzanine package. Nevertheless, the author of Metro-Mezzanine
shall NOT be held liable for whatever may happen on your computer
system or to any computer systems which connect to your own as a
result of operating the Metro-Mezzanine package. The user assumes
full responsibility for the correct operation of this software
package, whether harm or damage results from software error,
hardware malfunction, or operator error. NO warranties are offered,
expressly stated or implied, including without limitation or
restriction any warranties of operation for a particular purpose
and/or merchantability.
The Metro-Mezzanine main program, setup program, and documentation
are copyrighted products of Steven H. Lin. Steven H. Lin reserves
all rights to these products. This is protected by the United States
of America (USA) and International Copyright Laws. In no way shall
the components of the Metro-Mezzanine software package be reproduced
or modified in any form or method without prior expressly written
permission from Steven H. Lin.
Steven H. Lin grants an unlimited license for the purpose of dis-
tributing unregistered copies of the Metro-Mezzanine software
package to the public when such unregistered copies are released
from [The Deviant's Palace]. Tampering with or altering the contents
or integrity of the Metro-Mezzanine software package is prohibited.
No fee may be charged by any agency other than Steven H. Lin beyond
cost of distributing unregistered copies without prior expressly
written permission from Steven H. Lin.
Metro-Mezzanine is distributed under the Shareware concept. You are
allowed to operate Metro-Mezzanine for a trial period of thirty (30)
days. After this trial period, you must register Metro-Mezzanine or
discontinue its usage. Continued operation of Metro-Mezzanine past
the above stated trial period requires full registration payment.
The transfer of copyright ownership of Metro-Mezzanine from DevPal
MetroNet Communications, Inc. to the author of Metro-Mezzanine,
Steven H. Lin, does not in any way change the license agreement
explained above.
-----------------------------------------------------------------------------
2.0 REGISTRATION
Registration of Metro-Mezzanine is mandatory if you wish to continue using
Metro-Mezzanine past the thirty-day trial period. The unregistered demo
mode of Metro-Mezzanine is fully functional, but it lacks the many features
which are granted to registered sysops to further enhance the performance
and versatility of Metro-Mezzanine. To put it in another light, the un-
registered demo mode has the basic configuration for Metro-Mezzanine, while
the registered mode possesses the maximally-expanded configuration. Many
of the features mentioned in this text will apply only to the registered
version; when running the unregistered demo, it should be obvious which
capabilities are not included in the basic package.
There are different registration plans available, depending upon which
category your system falls into:
Non-Commercial System
Commercial System
System with Registered DevOnline Product(s)
After reading sections 2.1 - 2.4, complete the registration form at the
end of this document.
Issue a check or money order to STEVEN H. LIN.
Send the registration form and the check or money order to:
Steven H. Lin
DevPal MetroNet Communications
1251 NE 108th Street, #621
Miami, Florida 33161
United States of America
2.1 Instructions for Non-Commercial Systems -
To be considered a "non-commercial system", your system must be
physically located in a private residence and NOT be engaged in
commercial activities. These commercial activities include, but are
not limited to:
Subscription/registration REQUIRED for system access
Subscription/registration REQUIRED for access to a
part of the system
Product support for a product written or marketed by
the system operator(s) engaged in running, or aiding
in running, the system.
Product support for materials which the system operator(s)
have agreed to manage for the authors of those materials.
This includes ASP distribution sites.
The registration fees for a non-commercial system are:
$20.00 US
2.2 Instructions for Commercial Systems -
To be considered a "commercial system", your system must be
physically located in a non-private residence OR be engaged in
commercial activities. These commercial activities include, but
are not limited to:
Subscription/registration REQUIRED for system access
Subscription/registration REQUIRED for access to a
part of the system
Product support for a product written or marketed by
the system operator(s) engaged in running, or aiding
in running, the system.
Product support for materials which the system operator(s)
have agreed to manage for the authors of those materials.
This includes ASP distribution sites.
The registration fee for a commercial system is:
$35.00 US
2.3 Instructions for Systems with Registered DevOnline Product(s) -
Because of your registration of other DevOnline products, you have
enabled us to continue further development. As a gesture of thanks,
your registration fee for Metro-Mezzanine reflects your willingness
to support the authors of DevPal MetroNet Communications, Inc.
The registration fees for a system with registered DevOnline
product(s):
$10.00 US
2.4 Additional Costs -
In addition to registration of Metro-Mezzanine, there may be other
costs, depending on the method of delivery that you choose.
Delivery of registration key via FidoNet NetMail: FREE
Download of registration key from DevPalMiami : FREE
Complete registered version sent via USPS mail : $5.00 US
If you decide upon downloading the registration key from
DevPalMiami, remember to provide a filename and a security password
for the archive in which your key will be placed.
If you wish to access [The Deviant's Palace] at Miami computer system
metronetwork (AKA DevPalMiami), there are currently three accounts
available to DevOnline product registrants:
Basic status: 30-45 minutes per day
Regular status: 60 minutes per day
Executive/Preferred: 120 minutes per day
Each of the accounts have above-average downloading privileges, but
the Executive/Preferred account has by far the most lenient. All
subscription rates are discounted from their standard rates, so that
DevOnline registrants may take advantage of many of the special and
unique features at DevPalMiami.
-----------------------------------------------------------------------------
3.0 THE PURPOSE OF METRO-MEZZANINE
Metro-Mezzanine is a BBS carousel, in the tradition of Ghostwheel, the
earliest ever produced. Metro-Mezzanine's history is long and involved,
but it essentially begins with Ghostwheel, from which the Matrix login
method was adapted and also from which simple analogs were made by others.
Now the development cycle comes full circle, as Ghostwheel is now resurrected
for widespread use in the form of Metro-Mezzanine. Why settle for a poor
shade of Ghostwheel when you can have the successor to Ghostwheel?
But what is a BBS carousel? Whenever a sysop decides that operating more
than one BBS program is necessary (perhaps by joining different BBS programs
with different strengths together, the end effect is much greater than the
sum of the total, or perhaps more security is required than can be supplied
by one BBS program, or perhaps the sysop just wants to test out a new BBS
program with his enterprising users without having to drop his existing BBS
package and the users who wish to enjoy the status quo), a BBS carousel is a
logical solution. This is a program which allows the sysop to offer his users
the choice to access any of a number of BBS programs that are running on his
system, in a metronet-like fashion.
In addition, Metro-Mezzanine has other features which will aid the sysop in
directing his users:
An easy-to-use menu construction system, comparable to (but
simpler than) the TBBS/QuickBBS/RemoteAccess menu language.
The ability to display text files as well as jump to different
BBS programs, individually and in tandem.
The flexibility of errorlevels to initiate access to each
BBS program.
The ability to offer downloading of files specified by the sysop for
his users via Omen Technology's DSZ protocol subsystem.
3.1 Greater Utility in This Age of Technology -
The initial release of Metro-Mezzanine was never intended to make as
great an impact as it has. Unbeknownst to the author, there are
substantially more people eager for a BBS carousel than originally
estimated, by at least 580%. A major impact Metro-Mezzanine has made
is on systems operating within more than one mail network: the use of
Metro-Mezzanine to allow access to multiple BBS partitions, with
each partition operating within a different mail network, is
tremendously popular. DevPalMiami itself is able to operate within
several mail networks using different technologies (FidoNet, QWK,
ExecNet, and VBBS methods) because of Metro-Mezzanine. This
incredible expansion of connectivity and configurability frees
sysops from needing all sorts of ugly, kludgy methods of trying to
tie together different technologies and lets them concentrate on the
important aspects of running a colorful, diversified system. If you
want to operate your system within more than one mail network, then
Metro-Mezzanine is an excellent option for you.
-----------------------------------------------------------------------------
4.0 REQUIREMENTS
4.1 General System Requirements -
The following are the requirements for using Metro-Mezzanine:
An MS-DOS computer
A modem
At least one BBS program or telecommunications host package
A front-end/mailer (eg. FrontDoor, BinkleyTerm)
An ANSI driver
At least 200Kb of hard disk space...
(can be run from floppy, but what about the BBS's?)
As much RAM as needed for the most memory-requiring of the
BBS programs or telecommunications host packages used
4.2 Environments -
Metro-Mezzanine will work under the following environments (although
it is certainly not limited to only the following):
Artisoft LANtastic 3.3 - 4.1
Compaq MS-DOS 3.31
Digital Research DR-DOS 5.0 - 6.0
Microsoft MS-DOS 3.3 - 5.0
Quarterdeck DesqView 2.31
4.3 Memory Managers -
Metro-Mezzanine appears well-behaved when operating under memory
management programs, such as HIMEM, QEMM-386, and NetRoom. This
is primarily because Metro-Mezzanine does not perform any unusual
operations in high memory areas (ie. extended memory, expanded
memory). It is also strongly advised that Metro-Mezzanine NOT be
loaded into any high memory areas.
-----------------------------------------------------------------------------
5.0 INSTALLATION
This is fairly simple: make a directory somewhere for the placement of
Metro-Mezzanine. Then unZIP the archive into that directory. At this point,
you are finished with the installation of the program.
-----------------------------------------------------------------------------
6.0 SETUP
Setup involves several steps:
Running the Metro-Mezzanine setup program (MEZSETUP) to initialize
the needed data files and to accept your choices for access in
Metro-Mezzanine.
Setting up your BBS batch file to handle Metro-Mezzanine.
Modifying DOOR information files to handle incoming callers.
6.1 The Metro-Mezzanine Setup Program -
In your Metro-Mezzanine directory, there is a program called
MEZSETUP.EXE. To run it, type the following at your DOS command
prompt:
MEZSETUP
You will be given a screen display announcing the program, then you
will asked to hit <ENTER>, whereupon you will be presented with the
main MezSetup menu.
Metro-Mezzanine, Type II has a few options at the main menu of its
setup program, and they are arranged as follows:
Metro-Mezzanine Setup -
---------------------
[A] Edit partition.
[B] Delete partition.
[C] Edit welcome file name.
[D] Edit menu file name.
[E] Edit command prompt.
[F] Edit protocol menu file name.
[G] Toggle registration screen.
[H] Set excessive C/R limit.
[Q]UIT Metro-Mezzanine Setup Program
(>
At the prompt (the "(>" symbol below the options), you may enter
the option you wish.
6.1.1 Edit partition -
"Partition" is the term applied to Metro-Mezzanine to
mean the different options available to users. A partition
may be an actual BBS partition (each individual BBS program
you are running) and the ability to access it, but that is
not necessarily true; it may be an order to display a text
file to the user.
This command allows you to provide Metro-Mezzanine with the
necessary options so that your users may perform whatever
functions you wish to allow them in the BBS carousel.
Since Metro-Mezzanine starts with NO preset partitions, but
rather lots of empty slots for the filling-in of
information, you will need to "edit in" your information.
Accessing the "Edit partition" feature will show you a list
of all available partitions to you for editing, then the
program will prompt you for your choice of which partition
to edit. In the unregistered version, there are ten (10)
available partitions for editing: 0 through 9. In the
registered version, there are forty (40) available parti-
tions: 0 to 39. Obviously, you get more versatility in the
registered version!
After you enter in the number of the partition which you
want to edit, you will see a display screen which shows you
both the present values for that particular partition and the
command you can use to change those values.
As an example: when prompted for the number of the partition
you wished to edit, you typed "18". After hitting <ENTER>,
you saw:
Partition #18 Information -
-------------------------
[A] Task Type : 0
[B] Partition Title : NONE
[C] Exits on Errorlevel : 0
[D] Text File Name : NONE
[E] Download File Name : NONE
[F] Partition Password : NONE
[G] Exiting String :
Accessing...
[Q]UIT
Edit which? :
Note that all of the values for Partition #18 have been
tared to default values. This is normal, since you have not
previously edited this partition (remember, this is the
first time you are setting up Metro-Mezzanine). Also note
that there is no need for you to activate consecutive
partitions: you can "jump around", skipping certain numbers
if you so wish. (eg. if you don't like the number "13", you
can completely ignore Partition #13 in your Metro-Mezzanine
setup, and consequently not have a Partition #13 for your
users to mess around with.)
6.1.1.1 Task Type -
The task type is the specifier you issue to
Metro-Mezzanine so it understands exactly what to do
when a user types in the command for that partition.
There are currently seven (7) simple task types that
you can choose from:
0 - keep the partition INACTIVE (not usable
by a user
1 - exit with errorlevel
2 - flash text file, then exit with error-
level
3 - flash text file
4 - download file via DSZ
5 - flash text file, confirm for exiting
with errorlevel, then either exit with
errorlevel or abort execution
6 - flash text file, confirm for downloading
a file with DSZ, then either download
file with DSZ or abort execution
Let us explore each of these tasks...
Type 0 is the default when the partition database
was first created. Type 0 is a null item: it makes
the partition inactive so that a user cannot do
anything if they type in that partition's number
at the Metro-Mezzanine command prompt (see section
7.0 on how users can navigate in Metro-Mezzanine).
Type 1 is a standard exit with an errorlevel. The
errorlevel that is used is specified by another
command in the "Edit partition" menu, "C". This is
the typical task type used for accessing a BBS
partition or another utility! It can also be used to
log out of your system, assuming that the errorlevel
used will match an errorlevel in your BBS batch file
that leads back to your mailer.
Type 2 consists of displaying a text file to the
user, followed by exiting with an errorlevel. This
option is good to use if you want your users to read
some information prior to accessing a BBS partition
(or logging out, or accessing another utility,
etc.). The text file is specified by another command
in the "Edit partition" menu, "D".
Type 3 is a standard text file display. It will
display a text file that you specify by another
command in the "Edit partition" menu, "D".
Type 4 is a file download option. The file that the
user downloads is specified by another command in
the "Edit partition" menu, "E". You MUST have DSZ
available, either in the Metro-Mezzanine directory
or somewhere along the DOS PATH, in order for this
to function properly. The actual protocol in the DSZ
package used for the transmission is determined by
another command in the "Edit partition" menu, "G".
Type 5 is a further combination of Type 3, a yes/no
prompting technique, and Type 1. Alternatively, it
could be seen as an elaborated Type 2 with a
confirmatory pause between the text file display and
the errorlevel exiting. The text file is specified
by another command in the "Edit partition" menu,
"D".
Type 6 combines Type 3 and Type 4 together, with an
confirmatory pause between the text file display and
the file downloading. The text file is specified by
another command in the "Edit partition" menu, "D";
the downloadable file is specified by the "E" command
in the same menu, and the actual protocol used is
specified in the "G" command.
6.1.1.2 Partition Title -
This is the entry in the Metro-Mezzanine menu that
the user sees. It is the name that you give to the
command. For example, using Partition #18 as a Type
1, you want Partition #18 to toss the user into your
QuickBBS system, which you've named "Lucifer! BBS".
So, for the partition title, you may want to enter:
Maximum length = 30 chars.
┌────────────────────────────┐
>Go into Lucifer! BBS
Note that you will have a maximum limit of thirty
(30) characters for the partition title, so make it
meaningful(?).
6.1.1.3 Exits on Errorlevel -
For those task types (1 and 2) which require an
errorlevel, this is where you have the opportunity
to enter it.
Note that you cannot assign any errorlevels between
1 and 9 inclusive, but 0 is a valid choice.
6.1.1.4 Text File Name -
For those task types (2, 3, 5, and 6) which require
a text file to be specified for display to the user,
this is where you have the opportunity to enter it.
It resembles the option for entering the partition
title:
Maximum length = 60 chars.
┌────────────────────────────────────────────── ...
>mezanine.doc
Note that there is a sixty (60) character limit for
the filename. This can include a drive specifier and
directory names; just make sure it fits within
twenty characters.
6.1.1.5 Download File Name -
For those task types (4 and 6) which require a
downloadable file to be specified for ZModem down-
load to the user, this is where you have the oppor-
tunity to enter it. It resembles the option for
entering the text file name:
Maximum length = 60 chars.
┌────────────────────────────────────────────── ...
>i:\file\devon\mezz021.zip
Note that there is a sixty (60) character limit for
the filename. This can include a drive specifier and
directory names; just make sure it fits within
twenty characters.
6.1.1.6 Partition Password -
The ability to safeguard partitions with security
passwords will was previewed in Type I but not
active. Now, in Type II, it IS active, and is very
useful for the security-minded sysop. It resembles
the option for entering the partition title:
Maximum length = 10 chars.
┌────────┐
>boo-hoo
Note that you can enter in the password in either
uppercase or lowercase, but the interface for
handling the password checks will be case-
insensitive.
6.1.1.7 Exiting String -
At the behest of many sysops who wanted to customize
each string presented to their users prior to
leaving Metro-Mezzanine on their way to a BBS
partition, this option has been included to allow
you to make whatever statement you wish. There is
a seventy (70) character limit to the length of the
string.
6.1.1.8 Note about extraneous information -
If you enter information for a partition that the
particular task type does not use, that information
is just ignored. For instance, if you entered an
errorlevel and a filename for a Type 1 task, you know
that the filename will be ignored because Type 1
tasks are standard exits using an errorlevel.
However, if you neglect to enter an errorlevel, your
setup may act "funny". On the other hand, you may
have deliberately entered the filename for the Type
1, with the purpose of later changing the partition
from a Type 1 task to a Type 2 task, which DOES use
the filename to display a text file to the user.
6.1.2 Delete partition -
Although you may have already guessed the purpose of this
command, you may not be familiar with how it works exactly.
Simply put, this command will tare the partition that you
specify. That's it. It does not actually delete the
partition from the database; the effect, however, is the
same, because the partition is marked as a Type 0.
6.1.3 Edit welcome file name -
Metro-Mezzanine includes an option for the sysop to include
a bulletin file or a title screen of his/her own design just
before the menu for Metro-Mezzanine appears but after the
program designator screen that appears first when a user
accesses the system. This option allows the sysop to rename
this "welcome file" from its default of WELCOME:
Current welcome file name: WELCOME
Maximum length = 8 chars. NO file extensions!
┌──────┐
>hello
Note that the prompt requires that you DO NOT add any file
extensions to the filename that you want to specify (in the
example above, "hello" is used). This is because Metro-
Mezzanine will allow you to design an ASCII version and an
ANSI version of the "welcome file", with the .ASC and .ANS
extensions respectively. Metro-Mezzanine will automatically
check for the extensions, so you only need to give the
filename without the extension.
6.1.4 Edit menu file name -
Metro-Mezzanine includes an option for the sysop to include
a menu file to replace the one dynamically generated as a
default:
Current menu file name: MENU
Maximum length = 8 chars. NO file extensions!
┌──────┐
>mm
Note that the prompt requires that you DO NOT add any file
extensions to the filename that you want to specify (in the
example above, "mm" is used). This is because Metro-Mezzanine
will allow you to design an ASCII version and an ANSI version
of the menu, with the .ASC and .ANS extensions respectively.
Metro-Mezzanine will automatically check for the extensions,
so you only need to give the filename without the extension.
6.1.5 Edit command prompt -
Metro-Mezzanine includes an option for you to alter the
appearance of part of the command prompt that appears to the
user after the menu (either the sysop-made menu file, or the
dynamically-generated default menu) is displayed.
Current command prompt: [*]:>
Maximum length = 20 chars.
┌──────────────────┐
>[DevPalMiami!]:
Note that there is a twenty (20) character limit to the
length of the prompt, but it should be sufficient for most
purposes. In later Metro-Mezzanine versions, the capacity of
the command prompt string may be expanded further. Also note
that there is no need to stick a <SPACE> character
immediately after the last character of the prompt: that
trailing <SPACE> is automatically placed by Metro-Mezzanine
when it displays your customized prompt!
6.1.6 Edit protocol menu file name -
Metro-Mezzanine includes an option for the sysop to include
a protocol menu of his/her own design whenever the AUTO
setting is selected for any file downloading task type.
This option allows the sysop to rename this "protocol menu"
from its default of PROTOCOL:
Current welcome file name: PROTOCOL
Maximum length = 8 chars. NO file extensions!
┌──────┐
>dl_prot
Note that the prompt requires that you DO NOT add any file
extensions to the filename that you want to specify (in the
example above, "dl_prot" is used). This is because Metro-
Mezzanine will allow you to design an ASCII version and an
ANSI version of the "welcome file", with the .ASC and .ANS
extensions respectively. Metro-Mezzanine will automatically
check for the extensions, so you only need to give the
filename without the extension.
6.1.7 Toggle registration screen -
Ever get tired of that registration information at the
beginning of every Metro-Mezzanine run? This option will let
you change it! When you access this option, you will be
presented with a short menu, allowing you to pick the type
of registration screen you'd like to present to the world.
There are three settings for the registration screen MODE:
0 - standard
1 - abbreviated
2 - customized
Let's explore each of these settings...
Type 0 is the default, and it is the same "boring"
registration information that has been displayed ever since
Type I (with changes to make it fit Type II, of course).
Type 1 is just a one-line description line, identifying the
program (Metro-Mezzanine), the program version, and the
program's last compilation date. This is very convenient for
the sysop who wants a no-nonsense presentation to his users.
Type 2 allows for you to make your own registration
information screen for Metro-Mezzanine. If you input "2" as
your setting, another option will appear in the menu for
this section: filename for the registration screen. It is
set to a default of "REGINFO.ASC". You may change the
filename to fit your personal tastes. Note that this screen
should preferably be in ASCII, in case some of your users do
not have ANSI capabilities or prefer NOT to see your
registration information screen in ANSI.
6.1.8 Set excessive C/R limit -
Sometimes some users derive immense joy from whacking the
<ENTER> key excessively. While this is great fun for them,
it may be annoying to you, especially if you happen to pass
by and notice the ridiculous tomfoolery on your monitors.
What may be worse is that it could be due NOT to the user's
antics but a real connection problem. Rather than agonize
over this, you can set the excessive C/R limit value to
whatever you wish, so that the user will be logged out if
there are too many carriage returns sent to your system.
6.2 Setting up your BBS batch file -
This is a crucial step, because if this is improperly set up, your
system will not function well with Metro-Mezzanine. However, luckily,
this is an easy step, too.
Include the following paradigm in the BBS batch file that you use to
access your BBS's:
CD <Metro-Mezzanine directory>
MEZZ <DOOR info file>
If errorlevel <errorlevel value> goto <BBS routine>
If errorlevel <errorlevel value> goto <BBS routine>
If errorlevel <errorlevel value> goto <BBS routine>
If errorlevel <errorlevel value> goto <BBS routine>
If errorlevel <errorlevel value> goto <BBS routine>
.
. (repeat as many times as needed)
.
The "CD" command is used to switch the system focus into the Metro-
Mezzanine directory, so that the next line can work to activate
Metro-Mezzanine.
The second line, incidentally, will require a DOOR information
file... one of the following:
DOOR.SYS
DORINFO?.DEF
PCBOARD.SYS
or
GENERIC.SYS
If your mailer is capable of producing one of the first three DOOR
info files, then by all means, have it do so. If not, there are some
programs available which will be able to manufacture dummy DOOR info
files if given baud rate and comm port information. Or, you may take
one of the DOOR info files that your BBS program makes and modify it
to match different baud rates and/or comm ports, using your batch
file to copy the right file for use by Metro-Mezzanine. Or, even
more basic would be to use GENERIC.SYS to run Metro-Mezzanine. Let's
explore these options...
6.2.1 Mailer capable of making DOOR information file -
This is the simplest option: just have the mailer
manufacture of the first three listed DOOR info files, and
you're all set.
6.2.2 Dummy DOOR information file generation program -
This is a good method, too. Make sure that you inform this
program as to what the baud rate and comm port assignments
are.
Here is an example of the BBS batch file portion used to
impart information to Metro-Mezzanine using one of these
dummy generators:
CD H:\FD\MEZZ
MakDRSYS 2400 COM2:
MEZZ DOOR.SYS
.
.
.
6.2.3 Copying over DOOR information files -
You can grab a DOOR info file used by your BBS (these are
rarely deleted whenever a user returns from a DOOR) and take
a look inside it. Go ahead and modify it to match the
different baud rates and/or comm ports used by your BBS.
For instance, you run a 2400-9600 baud system (okay, it
comes to two basic baud rates... 2400 and 9600) on COM1:. So
you grab yourself a copy of DOOR.SYS that your BBS makes for
some DOORs. You change the baud rate line to reflect 2400
baud, then save to another name (D2400.SYS). You do the same
thing for 9600 baud (saved to D9600.SYS). Since the DOOR
info file already had correct comm port assignment (COM1:),
you did not have to change that.
The following is a BBS batch file portion which uses this
method. It assumes that the baud rate is being passed to it
from the mailer directly or the mailer batch file.
CD \FD\MEZZ
If %1==2400 copy D2400.SYS DOOR.SYS
If %1==9600 copy D9600.SYS DOOR.SYS
Mezz DOOR.SYS
.
.
.
6.2.4 GENERIC.SYS -
This is a special text file used by Metro-Mezzanine in lieu
of the other methods mentioned above. It contains three
lines:
line 1 - <sysop name>
line 2 - comm port
line 3 - time allowed (in minutes) in M-M
A sample GENERIC.SYS might read:
Steve
COM2:
60
The following is a sample BBS batch file portion which uses
the GENERIC.SYS file:
CD \BT\MEZZ
Mezz GENERIC.SYS
.
.
.
Frankly, this method is the preferred one at DevPalMiami
because FrontDoor cannot self-generate any DOOR information
files, and we would rather not have to spend time copying
over DOOR information files from elsewhere. Also,
GENERIC.SYS gives us more control over Metro-Mezzanine
access, making it even for everybody. If you do not know
which method of configuring Metro-Mezzanine (a DOOR
information file from your mailer, a copied-over DOOR
information file, or GENERIC.SYS), it is suggested that you
use GENERIC.SYS.
WARNING: Keep the time allowed under 250 minutes!
6.2.5 About errorlevels -
The following line:
If errorlevel <errorlevel value> goto <BBS routine>
can be used as many times as needed. The <errorlevel value>
holds whatever errorlevel you specified in MezSetup, while
the <BBS routine> is the batch label that is accessed
because of that errorlevel. Be careful to make sure that the
errorlevels are properly matched to their corresponding
labels.
6.3 Non-standard communications port support -
Section 6.2 explains how to set up M-M using a vanilla setup, which
works perfectly for most people. However, for the exceptions who,
for some strange reason, need (or want) to use a non-standard serial
communications port to handle the interface between the modem and the
computer, here is the paradigm to do so:
MEZZ <DOOR info file> PORT:<port address>:<port number>
The <DOOR info file> parameter is for the complete path and filename
of the DOOR info file desired for use. The <port address> is the
actual base memory address for the serial port. The <port number> is
the integer of the serial port which you wish to use for the BBS
carousel.
For instance:
MEZZ h:\fd\mezz\generic.sys PORT:03F8:5
This means that M-M is using the GENERIC.SYS file for getting per-
tinent information from the BBS, and the non-standard comm port is
accessed at memory location 03F8, and the comm port is known as
COM5:.
Check the documentation for the non-standard serial port you intend
to use for the correct way to install that serial port on your
system.
6.4 DigiBoard support -
Section 6.2 explains how to set up M-M using a vanilla setup, which
works perfectly for most people. However, for the exceptions who,
for some strange reason, need (or want) to use a DigiBoard to handle
the interface between the modem and the computer, here is the
paradigm to do so:
MEZZ <DOOR info file> PORT:D:<port number>
The <DOOR info file> parameter is for the complete path and filename
of the DOOR info file desired for use. The <port address> is the
actual base memory address for the serial port. The <port number> is
the integer of the serial port which you wish to use for the DOOR.
For instance:
MEZZ g:\bt\mezz\pcboard.sys PORT:D:4
This means that M-M is using the PCBOARD.SYS file for getting per-
tinent information from the BBS, and the DigiBoard channel being
used for M-M is #4.
Check the DigiBoard documentation for the correct way to install
it and to use it on your system.
-----------------------------------------------------------------------------
7.0 OPERATIONS
Now you should be ready to try out Metro-Mezzanine for the first time.
Either have a user call in, or try it yourself. If you want to try it
locally (instead of using another modem or phone line to call into your
BBS), make a dummy DOOR info file (mentioned in section 6.2) and slip in
"COM0:" to represent the comm port. That will make Metro-Mezzanine recognize
that you are a local user. The batch file used to run Metro-Mezzanine does
not have to be modified.
When the user logs into your system, they encounter the mailer you use
first. Then the mailer will drop them into Metro-Mezzanine. When Metro-
Mezzanine is run, the user is shown a title screen, which requires that he
hit <ENTER> to continue. After hitting <ENTER>, he is presented with the
list of available partitions (set by you using MezSetup). At the command
prompt, he can type whatever option he wishes, whereby he is presented with
the action specified by that partition.
Sounds confusing? Okay, let's do a trial run:
A user calls into your system. He sees FrontDoor, hits <ESC> a few
times, and is escorted from FrontDoor into Metro-Mezzanine. Once
there, he sees a title screen and is asked if he has ANSI
capabilities. After that, he is exposed to your custom-made welcome
file. Once the welcome file is finished displaying, he hits <ENTER>
to continue into the main part of Metro-Mezzanine. Because you
decided to stick with Metro-Mezzanine's dynamically-generated default
menus, you did not provide any menu files to Metro-Mezzanine. Here
is the resulting menu screen:
--- Metro-Mezzanine ---
[0] HELP! (command summary)
[1] NEW USER ACCESS!
[2] Enter NightVeil PCB
[3] Enter Process Bank RA
[10] Read DevPalMiami's Objectives
[11] Read about DevOnline Products
[20] D/L Arm of the Dragon
[21] D/L Coherence *
[22] D/L Flumen Musae Novae
[23] D/L Metro-Mezzanine
[24] D/L TeraCorps
[38] TeraCorps File Transmission *
[39] GOODBYE!
(0 used, 60 left) [DevPalMiami!]: _
Note that each of the commands are actually the number of each
partition available to the user, and there is no need for the
partitions to be made consecutively (notice the gaps between
Partition #3 and #10, #11 and #20, and #21 and #39).
Here's an explanation of each of the partitions shown above:
Partition #0 is a Type 3... it shows a text file called
MEZANINE.HLP to the user. This text file is a short
description of the other options available to the user
in Metro-Mezzanine.
Partition #1 is a Type 2... it shows a text file called
NV.TXT to the user. This text file explains what the New
User Access system is (it actually is the NightVeil PCBoard
system, which appears as another option just below). If a
user is totally confused as to what to do, this is a good
place for him to go.
Partition #2 is a Type 5... it resembles Partition #1 in
functionality, except that after it shows the text file
(still NV.TXT) to the user, it asks him if he wishes to
access the NightVeil PCBoard BBS partition. If not, he is
returned to the main Metro-Mezzanine menu.
Partition #3 is also a Type 5... it resembles Partition #2
in that it flashes a text file to the user (this time, it is
PROC.TXT, which describes the features to be found in the
Process Bank RemoteAccess BBS partition), followed by asking
him if he would like to access the Process Bank. If not, he
is returned to the main Metro-Mezzanine menu.
Partitions #10 and #11 are Type 3, resembling Partition #0
in that they display text files to the user, but these two
text files are different in content.
Partitions #20, #22, #23, and #24 are Type 6. They flash a
text file to the user, basically descriptions of the files
that the user may download. After the text file display,
the user is asked if he would like to download the file
concerned. If not, he is returned to the main Metro-
Mezzanine menu. If he does want to download the file, he
is presented with a protocol menu, from which he chooses
his desired protocol. Then the downloading may proceed...
Partition #21 is special: it is a passworded partition Type
6. This is because the Coherence Project is in alpha-
testing, and we are making the latest Coherence releases
available only to our alpha testers. Thus, we have given
the security password to our alpha testers; no one else
will be able to download the Coherence Project files. We
use the text file display to tell our alpha testers about
the latest improvements to the files they are about to
download.
Partition #38 is also special: it is a passworded partition
Type 4. Since we are running the TeraCorps inter-BBS
online/offline game, it is important to allow non-FidoNet
type systems access to their daily game/mail packets. Al-
though they are not able to conduct mail sessions with our
mailer, they can run a communications program through a
script file (eg. Telix) everyday to access DevPalMiami and
fetch their game/mail packets. Because we do not want others
(like regular users) to fetch these files, this partition
has been password-protected. The protocol has been set for
ZModem transferring because, then, the remote system can
take advantage of automatic ZModem downloading.
Partition #39 is actually a Type 1... it exits to an error-
level of 255, which is set in the BBS batch file to return
to the front-end/mailer of your BBS system, which will hang
up on the user. Session ended.
It's that simple!
7.1 Sysop Controls -
It would not be fair if the only the user was able to do things
while he is online... the sysop should have some features available
to himself, also. There are function keys which will give the sysop
some abilities while there is a user in Metro-Mezzanine. They are:
F5 - shell to DOS
F8 - exit Metro-Mezzanine
F9 - screen ON/OFF
F10 - chat with the user
There are some other keys available to PCBoard sysops. To see them,
hit Alt-H while in Metro-Mezzanine. They will appear in the status
bar at the bottom of your screen.
7.2 Protocol Selections -
. Metro-Mezzanine currently supports the usage of Omen Technology's
. excellent and tried-and-true protocol subsystem, DSZ. Although
. M-M Type II offered "designability" for sysops to custom-tailor
. command lines to operate DSZ, it was discovered many sysops have a
. difficult time figuring out exactly how to set up such command
. lines. To make the procedure less painful for sysops, M-M Type III
. has all of the DSZ protocols internally specified and optimized for
. the sysop. There is no need to specify any command line options for
. DSZ as a result. We hope that this is easier on you.
. However, in the future (ie. in non-alpha versions of M-M Type III),
. we will be adding support of more protocol subsystems, such as (but
. not limited to) SuperK, NModem, MPt, BiModem, TModem, Sam Smith's
. HS/Link, and even Omen's own GSZ (the graphical window display
. version of DSZ). There will be special security considerations to
. watch for, but those measures will be added as the need arises.
-----------------------------------------------------------------------------
8.0 VARIATIONS
Although Metro-Mezzanine is primarily for use as a BBS carousel, it can be
also used for other purposes:
8.1 As a "vestibule" for one-BBS systems so users do not have to take
lots of time to establish a real account on the BBS, but instead may
read the information left for potential users in Metro-Mezzanine
to determine whether he will log into the BBS and establish an
account.
eg. 1. Information about this BBS {Type 3}
2. Why do you want to join us? (Type 3)
3. Enter BBS (Type 1)
4. Hang up (Type 1)
8.2 As a "vestibule" for subscription systems so that the user, while
not able to actually enter into the BBS without prior arrangement
with the sysop or without a certain password, may be able to read
information left for potential users in Metro-Mezzanine by the sysop
and to download or screen capture a registration form.
eg. 1. Information about this BBS (Type 3)
2. Information on registration (Type 3)
3. Download registration form (Type 4)
4. Enter BBS (Type 2)
5. Disconnect (Type 1)
8.3 As a "crosswalk" between two or more BBS's when the user has already
entered one BBS and wants to go to another BBS without hanging up
his modem.
eg. 1. Transfer information (Type 3)
2. Go to BBS 1 (Type 5)
3. Go to BBS 2 (Type 5)
4. Go to BBS 3 (Type 5)
8.4 As a DOOR monitor for various DOORs.
eg. 0. About the DOORs (Type 3)
1. Go to DOOR 1 (Type 1)
2. Go to DOOR 2 (Type 1)
3. Go to DOOR 3 (Type 1)
4. Go to DOOR 4 (Type 1)
10. Return to BBS (Type 1)
8.5 As a software product distribution point, so callers do not have to
call into a full-blown BBS program and establish an account, just to
download one file. This is particularly handy for software authors
who wish to cater to a potential customers who are not in FidoNet
or a FidoNet-compatible mail network and are thus unable to perform
File Requests.
eg. 1. Enter support BBS (Type 1)
10. List of Products (Type 3)
11. Download Product 1 (Type 6)
12. Download Product 2 (Type 6)
13. Download Product 3 (Type 6)
19. Disconnect (Type 1)
8.6 Other uses -
Because of the nature of Metro-Mezzanine, many things are possible,
and the list of examples above is certainly not exhaustive. Multiply
the possible uses for Metro-Mezzanine by all of the different ways
to configure Metro-Mezzanine... you're looking at an infinite number
of setups!
-----------------------------------------------------------------------------
9.0 PRODUCT SUPPORT
To maintain his position as one of the most accessible shareware author, the
information following has been provided:
Address: Steven H. Lin, Ph.D., M.S.
DevPal MetroNet Communications
1251 NE 108th St., #621
Miami, FL 33161
BBS: [The Deviant's Palace] of Miami
305/899-1841
2400-14.4k HST/v.32bis
24 hours except ZMH
Voice: 305/899-0957
FN NetMail: FN 1:135/105.0
EN 50:5305/505.0
DN 55:55/1.0
DR 75:75/1.0
Internet: slinc@f135.n105.z1.fidonet.org
FN EchoMail: AOTD - DevOnline Products echo [DN/DR/FN]
DEV_SYSOP - DevNet Systems Operations echo [DN/FN]
DEV_TPA - Third Party Apps Developers echo [DN/FN]
DOORGAMES - DOOR Games Discussions echo [FN]
DOORWARE - DOORware echo [RN/FN]
D_UTIL - DOOR Utilities echo [DR]
PCBNET - PCBoard Sysops echo [FN]
RA_UTIL - RemoteAccess Utilities echo [FN]
U'NI-net/US: DOOR-UTIL - DOORs and utilities for BBS's
VirtualNet: 1 @3053
2 @3053
Voice support is given freely and is the preferred method of communication
by the author. Please take advantage of this remarkable avenue of support.
To further expand accessibility, there are now official DevOnline
distribution sites available to provide you with the latest unregistered
versions of DevOnline products:
DevOnCO (Mountain US) : The Hornet's Nest
sysop: Kevin Higgins loc: Fort Carson, CO
#: 719/579-0593 baud: 2400-14.4k HST
ice: TAG
addr: FN 1:128/74.0, VN 45:521/101.0
PCP: n/a
DevOnFL (Eastern US) : [The Deviant's Palace] of Miami
sysop: Steve Lin loc: Miami, FL
#: 305/899-1841 baud: 2400-14.4k HST/v.32bis
ice: Maximus-CBCS, PCBoard, QuickBBS, RemoteAccess,
WWIV-IMS, Virtual BBS, Waffle/DOS
addr: FN 1:135/105.0, EN 50:5305/505.0, DN 55:55/1.0,
UN DEVPAL, VtN @3053
PCP: FLMIA
DevOnTX (Southern US) : The Chess Board
sysop: Ken Givens loc: Grand Prairie, TX
#: 214/641-1136 baud: 2400-14.4k HST
ice: SuperBBS
addr: FN 1:1/132.0, FN 1:124/2213.0, 43:1370/101.0
PCP: TXDAL
DevOnVA (Mid-Atlantic US) : The NEOCOM Game Connection
sysop: David Fife loc: Martinsville, VA
#: 703/638-1952 baud: 2400-14.4k HST/9600 v.32
ice: RemoteAccess
addr: FN 1:264/615.0, DR 75:100/1.0
PCP: n/a
-----------------------------------------------------------------------------
10.0 ACKNOWLEDGEMENTS
All products mentioned in this text that are not produced by members of
DevPal MetroNet Communications, Inc. are trademarks of their respective
copyright holders and/or authors.
10.1 Dedication -
This program is dedicated to Wuu Shyong Lin, for having struggled so
long against insurmountable odds for his entire life and for
sacrificing everything he possessed and everything he was for his
family. Rest gracefully in peace.
10.2 And special thanks to (in alphabetical order)...
Michael Altschul, Ph.D. Rickie Belitz & DCIS
Cam N. DeBuck Gene de Libero
Ken Givens & The Chess Board Bonnie Hartstein & DevPalAnA
Corinna Harney & DevPalLV Norm Henke & PC-OHIO
John Hicks Kevin Higgins & The Hornet's Nest
Sil Horwitz Bruce Ikenaga, Ph.D.
Elaine Irwin Mary Lambert
Bob Mahoney & EXEC-PC Fred Maximilien
Omen Technology, Inc. PKWARE, Inc.
Herb Ritts
Mike Stewart, Ph.D., M.S. & DPBerk
John Theed Alejandra Torriano & DevPalDC
Ian Wells & TSanc Kari Wuhrer
... and to all of the very special sysops who picked up a copy of
Metro-Mezzanine
-----------------------------------------------------------------------------
11.0 FINAL WORDS
Metro-Mezzanine has a long way to go, in my opinion. It is not actually one
product, but rather a series of similar products geared toward facilitating
the access of BBS programs. No longer is a BBS program by itself considered
enough. Today's BBS's must have utility programs which enhance the its
performance many times over. Metro-Mezzanine fills a gap in an area which
has very few other comparable utilities; and Metro-Mezzanine, unlike its
competitors, is versatile and flexible enough to be used in more than a
single role. Until the advent of Metro-Mezzanine, there were generally
considered to be only EIGHT programs which acted as BBS carousels. One of
them was Ghostwheel and thus unavailable to the public and, anyways, it was
over three megabytes in size and required the concurrent setup of MS-DOS and
UNIX/386; two others were not actually programs... they were clever but
difficult-to-manage and problematic ways to manipulate batch files and
certainly not very comfortable nor reliable for sysops; another was a way
of fooling a certain mailer's own external mail routines to think the
incoming caller was a mail run, and thus offered very little in the way of
amenities or security; two were actually optional menus configured into BBS
programs but were not robust enough to handle all callers faultlessly and
were not flexible enough to be used to handle situations except as user
screening devices; the author of another disappeared a short time after
his product was released; and the last one was extremely overpriced for
the limited features it offered and its author also vanished abruptly.
Metro-Mezzanine represents the first true attempt to provide a versatile
pre-BBS and/or inter-BBS interface robust enough for handling many
different situations.
Feel free to experiment. Metro-Mezzanine was not developed for sysops who
like to have bland, monotonous systems: it was meant for the enterprising,
inspired sysops who believe that they have something special to offer to
others. It is the pioneering spirit of Modemland that Metro-Mezzanine caters
to, not the evils of stagnation.
Happy designing!
- Steven H. Lin, Ph.D., M.S.
-----------------------------------------------------------------------------
METRO-MEZZANINE, Type III
Registration Form 3E - Version 3.08
DevOnline Product MEZZ-X3
Sysop Name _________________________________________________________________
BBS Name ___________________________________________________________________
BBS Phone Number ___________________________________________________________
BBS City, State ____________________________________________________________
Sysop's Address ____________________________________________________________
(no P.O. Boxes) ____________________________________________________________
____________________________________________________________
Sysop's Voice Phone Number(s) ______________________________________________
____________________________________________________________________________
Any Mail Network Addresses _________________________________________________
____________________________________________________________________________
Indicate which registration option(s) you'd like by CIRCLING the correct
number(s) below:
#1 - Non-commercial registration [$20.00 US]
#2 - Commercial registration [$35.00 US]
#3 - DevOnline preferred registration [$10.00 US]
#4 - Normal USER status on DevPal [FREE] \
#5 - One year standard registration on DevPal [$8.00] > pick one
#6 - One year preferred registration on DevPal [$12.00] /
#7 - Consideration for beta test site [FREE]
#8 - USPS mail delivery of disk (see below) [$5.00] OPTIONAL
Total cost: ___________________________
Your System Hardware (be specific!)_________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
Your BBS Software (be specific!)____________________________________________
____________________________________________________________________________
Registered Key Delivery: _____ via File Attach (a la FidoNet)
_____ I prefer maximum security... Hold my copy on
DevPalMiami so I can d/l it myself. Name the
M-M reg. key file __________________________
and encrypt it with the password ___________
and put the file in the DevOnline file area
on NightVeil PCBoard BBS partition!
_____ Send my copy to me by mail. I understand
that I will pay US $5.00 for S&H if I am in
the U.S. and US $10.00 for S&H if I am out-
side the U.S.
Signature ___________________________________ Birthdate ____________________